https://modernanalyst.com RSS feeds for Business Analyst Community & Resources | Modern Analyst 60 https://modernanalyst.com/Resources/Articles/tabid/115/ID/639/What-happens-to-the-role-of-the-Business-Analyst-in-an-Agile-Utopia.aspx#Comments 8 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=639 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=639&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/639/What-happens-to-the-role-of-the-Business-Analyst-in-an-Agile-Utopia.aspx If Agile is to become the next zeitgeist for development, what will become of the traditional Business Analyst? We all know the traditional waterfall mantra: analyze, design, build then test... underpinned by the common belief that the more you analyze up front the more you save in maintenance later on. This has had a huge impact on the way we organize our teams: separating functions and putting a heavy emphasis on theoretical modeling. When a project kicks off, the classic Gantt chart dictates that analysts are on-boarded early for a lengthy requirements analysis stage. Once the requirements specification is 'signed off' the analysts are often relieved of their posts for the design crew to take over. The 'sign off' fest continues until eventually the user community is (invariably) force fed a UAT phase and the fledgling product is launched; all the while resources are inhaled and exhaled as the project plan demands. The project then becomes more of a way to co-ordinate a set of individual skill sets and activities. colart Sat, 10 Jan 2009 13:06:00 GMT f1397696-738c-4295-afcd-943feb885714:639